Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1102

reference
929-tree-1
name
1102
tree-preservation-order

undefined

929-tpo-1
uprn
address-text
point
POINT (-1.010559 50.886893)
geometry
MULTIPOLYGON (((-1.010488 50.886886,-1.010491 50.886900,-1.010501 50.886912,-1.010517 50.886922,-1.010536 50.886929,-1.010558 50.886931,-1.010580 50.886929,-1.010600 50.886923,-1.010616 50.886913,-1.010627 50.886901,-1.010630 50.886887,-1.010627 50.886873,-1.010617 50.886860,-1.010602 50.886850,-1.010582 50.886844,-1.010560 50.886841,-1.010538 50.886843,-1.010518 50.886849,-1.010502 50.886859,-1.010492 50.886872,-1.010488 50.886886)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL